Access control

Access control

The access control offers possibilities for monitoring the system. The following can be logged

• the call of a module
• the call or change of an object
• the use of a specific functionality

The corresponding log entries are written into the LogFile of the logged-in user and can thus be evaluated.

The auditing module (auditing.mod), which is also used to audit data processing, is responsible for access control. The access control is activated by sending the message "START_AUDITING_SILENT" and the parameter TRUE, it is terminated by the same message and the parameter FALSE. Since the control mechanism should usually apply to an entire session, it is recommended that you call it directly in the project file *.CXP.

The auditing module is used to define which messages are to be monitored. This definition should be made individually in the customer derivation. Once the module is active, it automatically becomes the recipient of all globally sent messages (broadcasts). For the messages to be tracked, the corresponding actions must be defined in the module and a corresponding log entry must be created.

The structure of the entry in the entry in the LogFile then looks as follows:
<Date> <Time> <Process ID> INFO cx.app - <Log entry>

The <log entry> is a character string that is generated by the auditing module. Important for the structure of this entry is the use of keywords in order to be able to perform a better evaluation afterwards. For example, the log entry for the call of the sales article 123456 could look like this:
<Date> <Time> <Process ID> INFO cx.app - MSG_AUDITING::EDIT_SALES_ITEM::123456